System for restructuring electronic data elements within a mutable hierarchical database

ABSTRACT

A system provides for restructuring electronic data elements within a mutable hierarchical database. In particular, the system may dynamically perform perspective-based restructuring the database depending on the status and/or identity of the user or computing system that is accessing the database. In this regard, the system may use an artificial intelligence and/or machine learning application to progressively modify relationships and/or attributes of data elements within the database to create multiple configurations or arrangements of database structures along certain perspectives and/or dimensions. Once the multiple configurations are generated, the system may allow the data structures to be dynamically adjusted based on the perspective or purpose for which the database is accessed.

FIELD OF THE INVENTION

The present disclosure embraces a system for restructuring electronicdata elements within a mutable hierarchical database.

BACKGROUND

Data structures within conventional databases are typically rigidlyfixed in the configuration specified at the time in which the databasesare first constructed. That said, it may be desirable to change theconfiguration of data structures dependent on the user and/or computingsystem that accesses the databases. Accordingly, there is a need for away to dynamically restructure data elements and structures withindatabases.

BRIEF SUMMARY

The following presents a simplified summary of one or more embodimentsof the invention in order to provide a basic understanding of suchembodiments. This summary is not an extensive overview of allcontemplated embodiments, and is intended to neither identify key orcritical elements of all embodiments, nor delineate the scope of any orall embodiments. Its sole purpose is to present some concepts of one ormore embodiments in a simplified form as a prelude to the more detaileddescription that is presented later.

The present disclosure is directed to a system for restructuringelectronic data elements within a mutable hierarchical database. Inparticular, the system may dynamically perform perspective-basedrestructuring the database depending on the status and/or identity ofthe user or computing system that is accessing the database. In thisregard, the system may use an artificial intelligence and/or machinelearning application to progressively modify relationships and/orattributes of data elements within the database to create multipleconfigurations or arrangements of database structures along certainperspectives and/or dimensions. Once the multiple configurations aregenerated, the system may allow the data structures to be dynamicallyadjusted based on the perspective or purpose for which the database isaccessed.

According, embodiments of the present disclosure provide a system forrestructuring electronic data elements within a mutable hierarchicaldatabase. The system may comprise a memory device with computer-readableprogram code stored thereon; a communication device; and a processingdevice operatively coupled to the memory device and the communicationdevice. The processing device may be configured to execute thecomputer-readable program code to generate the mutable hierarchicaldatabase, wherein the mutable hierarchical database comprises one ormore data elements; receive a first request to access the mutablehierarchical database; based on the first request, create a firstconfiguration of the data elements within the mutable hierarchicaldatabase; receive a second request to access the mutable hierarchicaldatabase; and based on the second request, create a second configurationof the data elements within the mutable hierarchical database.

In some embodiments, the one or more data elements comprise nodes,edges, and properties, wherein creating the first configuration of thedata elements and creating the second configuration of the data elementscomprises at least one of adding nodes, removing nodes, modifyingrelationships, modifying properties, or changing hierarchical positionsof nodes.

In some embodiments, the first request is associated with a firstobjective and submitted by a first user, wherein the first configurationof the data elements is associated with the first objective, wherein thesecond request is associated with a second objective and submitted by asecond user, wherein the second configuration of the data elements isassociated with the second objective.

In some embodiments, the computer-readable program code further causesthe processing device to present the first configuration of the dataelements to the first user; and present the second configuration of thedata elements to the second user.

In some embodiments, the first request is associated with a firstobjective and submitted by a first user, wherein the first configurationof the data elements is associated with the first objective, wherein thesecond request is associated with a second objective and submitted bythe first user, wherein the second configuration of the data elements isassociated with the second objective.

In some embodiments, the computer-readable program code further causesthe processing device to present the first configuration of the dataelements and the second configuration of the data elements to the firstuser.

In some embodiments, the computer-readable program code further causesthe processing device to store the first configuration of the dataelements and the second configuration of the data elements within aconfiguration repository.

Embodiments of the present disclosure also provide a computer programproduct for restructuring electronic data elements within a mutablehierarchical database. The computer program product may comprise atleast one non-transitory computer readable medium havingcomputer-readable program code portions embodied therein, thecomputer-readable program code portions comprising executable codeportions for generating the mutable hierarchical database, wherein themutable hierarchical database comprises one or more data elements;receiving a first request to access the mutable hierarchical database;based on the first request, creating a first configuration of the dataelements within the mutable hierarchical database; receiving a secondrequest to access the mutable hierarchical database; and based on thesecond request, creating a second configuration of the data elementswithin the mutable hierarchical database.

In some embodiments, the one or more data elements comprise nodes,edges, and properties, wherein creating the first configuration of thedata elements and creating the second configuration of the data elementscomprises at least one of adding nodes, removing nodes, modifyingrelationships, modifying properties, or changing hierarchical positionsof nodes.

In some embodiments, the first request is associated with a firstobjective and submitted by a first user, wherein the first configurationof the data elements is associated with the first objective, wherein thesecond request is associated with a second objective and submitted by asecond user, wherein the second configuration of the data elements isassociated with the second objective.

In some embodiments, the computer-readable program code portions furthercomprise executable code portions for presenting the first configurationof the data elements to the first user; and presenting the secondconfiguration of the data elements to the second user.

In some embodiments, the first request is associated with a firstobjective and submitted by a first user, wherein the first configurationof the data elements is associated with the first objective, wherein thesecond request is associated with a second objective and submitted bythe first user, wherein the second configuration of the data elements isassociated with the second objective.

In some embodiments, the computer-readable program code portions furthercomprise executable code portions for presenting the first configurationof the data elements and the second configuration of the data elementsto the first user.

Embodiments of the present disclosure also provide acomputer-implemented method for restructuring electronic data elementswithin a mutable hierarchical database. The method may comprisegenerating the mutable hierarchical database, wherein the mutablehierarchical database comprises one or more data elements; receiving afirst request to access the mutable hierarchical database; based on thefirst request, creating a first configuration of the data elementswithin the mutable hierarchical database; receiving a second request toaccess the mutable hierarchical database; and based on the secondrequest, creating a second configuration of the data elements within themutable hierarchical database.

In some embodiments, the one or more data elements comprise nodes,edges, and properties, wherein creating the first configuration of thedata elements and creating the second configuration of the data elementscomprises at least one of adding nodes, removing nodes, modifyingrelationships, modifying properties, or changing hierarchical positionsof nodes.

In some embodiments, the first request is associated with a firstobjective and submitted by a first user, wherein the first configurationof the data elements is associated with the first objective, wherein thesecond request is associated with a second objective and submitted by asecond user, wherein the second configuration of the data elements isassociated with the second objective.

In some embodiments, the method further comprises presenting the firstconfiguration of the data elements to the first user; and presenting thesecond configuration of the data elements to the second user.

In some embodiments, the first request is associated with a firstobjective and submitted by a first user, wherein the first configurationof the data elements is associated with the first objective, wherein thesecond request is associated with a second objective and submitted bythe first user, wherein the second configuration of the data elements isassociated with the second objective.

In some embodiments, the method further comprises presenting the firstconfiguration of the data elements and the second configuration of thedata elements to the first user.

In some embodiments, the method further comprises storing the firstconfiguration of the data elements and the second configuration of thedata elements within a configuration repository.

The features, functions, and advantages that have been discussed may beachieved independently in various embodiments of the present inventionor may be combined with yet other embodiments, further details of whichcan be seen with reference to the following description and drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described embodiments of the invention in general terms,reference will now be made to the accompanying drawings, wherein:

FIG. 1 illustrates an operating environment for the mutable databasesystem, in accordance with one embodiment of the present disclosure;

FIG. 2A illustrates a set of data elements within a first configurationof the mutable hierarchical database, in accordance with one embodimentof the present disclosure;

FIG. 2B illustrates the set of data elements within a secondconfiguration of the mutable hierarchical database, in accordance withone embodiment of the present disclosure; and

FIG. 3 illustrates a process flow for the mutable database system, inaccordance with one embodiment of the present disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

Embodiments of the present invention will now be described more fullyhereinafter with reference to the accompanying drawings, in which some,but not all, embodiments of the invention are shown. Indeed, theinvention may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure will satisfy applicablelegal requirements. Like numbers refer to elements throughout. Wherepossible, any terms expressed in the singular form herein are meant toalso include the plural form and vice versa, unless explicitly statedotherwise. Also, as used herein, the term “a” and/or “an” shall mean“one or more,” even though the phrase “one or more” is also used herein.

“Entity” as used herein may refer to an individual or an organizationthat owns and/or operates an online system of networked computingdevices, systems, and/or peripheral devices on which the systemdescribed herein is implemented. The entity may be a businessorganization, a non-profit organization, a government organization, andthe like, which may routinely use various types of applications withinits enterprise environment to accomplish its organizational objectives.

“Entity system” as used herein may refer to the computing systems,devices, software, applications, communications hardware, and/or otherresources used by the entity to perform the functions as describedherein. Accordingly, the entity system may comprise desktop computers,laptop computers, servers, Internet-of-Things (“IoT”) devices, networkedterminals, mobile smartphones, smart devices (e.g., smart watches),network connections, and/or other types of computing systems or devicesand/or peripherals along with their associated applications.

“Computing system” or “computing device” as used herein may refer to anetworked computing device within the entity system. The computingsystem may include a processor, a non-transitory storage medium, acommunications device, and a display. The computing system may beconfigured to support user logins and inputs from any combination ofsimilar or disparate devices. Accordingly, the computing system may be aportable electronic device such as a smartphone, tablet, single boardcomputer, smart device, or laptop. In other embodiments, the computingsystem may be a stationary unit such as a personal desktop computer,networked terminal, IoT device, or the like.

“User” as used herein may refer to an individual who may interact withthe entity system to access the functions therein. Accordingly, the usermay be an agent, employee, associate, contractor, or other authorizedparty who may access, use, administrate, maintain, and/or manage thecomputing systems within the entity system. In other embodiments, theuser may be a client or customer of the entity.

Accordingly, as used herein the term “user device” or “mobile device”may refer to mobile phones, personal computing devices, tabletcomputers, wearable devices, and/or any stationary or portableelectronic device capable of receiving and/or storing data therein.

“Neural network” as referred to herein may refer to a network ofcomputing nodes that use artificial intelligence and/or machine learningalgorithms to accomplish certain tasks. Broadly, neural networks may beused for tasks requiring pattern recognition. For instance, a neuralnetwork may be constructed and used for the purposes of speechrecognition, facial recognition, fraud detection, machine translation,gaming AI, or the like.

“Node” or “vertex” as used herein may refer to a functional data unitwithin a graph database, where the vertices may be connected to oneanother via “edges” or “lines” which establish certain definedrelationships between vertices. For instance, a node labeled “server”may be connected to a node named “client” via an edge indicating thatthe server is configured to communicatively provide a resource (e.g.,data) to the client. In some embodiments, the nodes and/or the edges maybe associated with one or more “properties” which further adddescriptive information to the nodes and/or edges.

Embodiments of the present disclosure provide a system for restructuringelectronic data elements within a mutable hierarchical database. Adatabase, which in some embodiments may be a hierarchical graphdatabase, may contain one or more data entries (e.g., nodes) which haveone or more defined attributes (e.g., properties). Each of the one ormore data entries may be connected to other data entries byrelationships, where the relationships indicate that the data entriesare related along a defined dimension (e.g., hierarchical relationshipssuch as “parent-child”). In this regard, properties may further beassigned to relationships to add further dimensions to eachrelationship.

In generating such a database, the system (which may be referred toherein as the “mutable database system”) may be used to provide aninitial structure or configuration for data entries (e.g., nodes,properties, relationships between nodes, or the like) from an initialviewpoint (e.g., a perspective of an initial user, dimension, use case,or the like). Within the initial structure, the data entries may bearranged into a hierarchical structure with certain nodes being onhigher and/or lower levels within the hierarchy. Certain nodes mayfurther have cross-level relationships (e.g., parent, child, or thelike) with other nodes.

After generating the initial structure, the system may, via AI/machinelearning models, add properties to certain data elements (e.g., nodes,relationships, or other properties). The added properties may identifythe configuration or position of the data elements when the database isviewed from a different perspective or dimension from the perspective ordimension from which the database was initially viewed during theconstruction of the initial structure of the database. In this way, saidadded properties may cause the data elements to be restructureddepending on the perspective from which the database is viewed oraccessed. For example, certain data elements, when viewed from adifferent perspective, may be placed higher or lower in the hierarchy,may be related to different data elements, or may be present or absentin the structure entirely, depending on who is accessing the database,the purpose for accessing the database, and/or what type of data recordsare queried, or the like. In this way, a second configuration of dataelements may be created which may be specific to the environment and/orcircumstances in which the database is accessed. The process asdescribed above may be iterated to generate additional configurations ofdata elements (e.g., a third configuration, fourth configuration, or thelike) to account for various additional perspectives or conditions inwhich the database may be accessed. In some embodiments, at least aportion of each configuration may be saved in a saved state. In otherembodiments, the database may be dynamically reconfigured for each queryor access request. By generating various structures or configurations ofthe data elements within the database, the system may generate a fluid,mutable database which may dynamically present the data entries withinthe database in different ways depending on the context in which thedatabase is accessed.

An exemplary use case is provided below for illustrative purposes. Inone embodiment, an entity may maintain a database of computingcapabilities related to data security. In such an embodiment, thedatabase may contain various data entries for capabilities as well astheir relationships to other capabilities. For instance, an initialconfiguration of the database may include a data entry may be made for achild node which represents root kit identification, where a parent node(e.g., an ability to detect malicious files or other threat vectors) maybe added in reference to the child node. In some embodiments, such arelationship may be tagged with additional properties to identify thesignificance of the relationship along certain vectors (e.g., datadiscovery vector). Once the initial configuration is completed, the dataentries may be reconfigured to account for different access scenarios.For example, if the database is subsequently viewed from a systemsstability viewpoint rather than a data security viewpoint, certain nodesmay be rearranged hierarchically in relation to other nodes,relationships may be altered, existing nodes may be exclude, and newnodes may be included (e.g., authentication credential requirements maybe more relevant to data security rather than systems stability). Insuch a manner, the system may generate multiple different configurationsof the same database which may be optimally suited for the user or thepurpose for which the database is accessed.

The system as described herein confers a number of technologicaladvantages over conventional database systems. By introducing mutabilityof data elements within the database, the system may dynamically providethe most relevant data in response to viewpoint-dependent accessrequests and/or queries. Furthermore, rearranging data elements mayallow the data elements within the database to be traversed with a muchgreater computing efficiency, thereby saving valuable system resources.

Turning now to the figures, FIG. 1 illustrates an operating environment100 for the mutable database system, in accordance with one embodimentof the present disclosure. In particular, FIG. 1 illustrates a mutabledatabase computing system 106 that is operatively coupled, via anetwork, to a first entity computing system 104 and/or an second entitycomputing system 103. In such a configuration, the mutable databasecomputing system 106 may transmit information to and receive informationfrom the first entity computing system 104 and/or the second entitycomputing system 103. It should be understood that FIG. 1 illustratesonly an exemplary embodiment of the operating environment 100, and itwill be appreciated that one or more functions of the systems, devices,or servers as depicted in FIG. 1 may be combined into a single system,device, or server. For instance, the functions of the first entitycomputing system 104 and the second entity computing system 103 may beexecuted on a single computing system. Furthermore, a single system,device, or server as depicted in FIG. 1 may represent multiple systems,devices, or servers. For instance, the mutable database computing system106 may represent multiple mutable database computing systems 106 whichhost a distributed database.

The network may be a system specific distributive network receiving anddistributing specific network feeds and identifying specific networkassociated triggers. The network include one or more cellular radiotowers, antennae, cell sites, base stations, telephone networks, cloudnetworks, radio access networks (RAN), WiFi networks, or the like.Additionally, the network may also include a global area network (GAN),such as the Internet, a wide area network (WAN), a local area network(LAN), or any other type of network or combination of networks.Accordingly, the network may provide for wireline, wireless, or acombination wireline and wireless communication between devices on thenetwork.

As illustrated in FIG. 1, the mutable database computing system 106 maycomprise a communication device 152, a processing device 154, and amemory device 156. The mutable database computing system 106 may beowned and/or operated by an entity such as an Internet service provider,financial institution, business organization, government agency, or thelike. As used herein, the term “processing device” generally includescircuitry used for implementing the communication and/or logic functionsof the particular system. For example, a processing device may include adigital signal processor device, a microprocessor device, and variousanalog-to-digital converters, digital-to-analog converters, and othersupport circuits and/or combinations of the foregoing. Control andsignal processing functions of the system are allocated between theseprocessing devices according to their respective capabilities. Theprocessing device may include functionality to operate one or moresoftware programs based on computer-readable instructions thereof, whichmay be stored in a memory device.

The processing device 154 is operatively coupled to the communicationdevice 152 and the memory device 156. The processing device 154 uses thecommunication device 152 to communicate with the network and otherdevices on the network, such as, but not limited to the first entitycomputing system 104 and/or the second entity computing system 103. Thecommunication device 152 generally comprises a modem, antennae, WiFi orEthernet adapter, radio transceiver, or other device for communicatingwith other devices on the network.

The memory device 156 may have computer-readable instructions 160 storedthereon, which in one embodiment includes the computer-readableinstructions 160 of a mutable database application 162 which allows theentity system to perform the database restructuring functions asdescribed herein. In some embodiments, the memory device 156 includesdata storage 158 for storing data related to the system environment. Inthis regard, the data storage 158 may comprise a mutable database 164,which may include various types of data used by the entity. Forinstance, the mutable database 164 may comprise data entries relating tocertain computing capabilities (e.g., detection of malicious code) andthe relationships of the capabilities with one another. Accordingly, insome embodiments, the mutable database 164 may comprise a graph databasein which the capabilities are stored as vertices and the associatedrelationships are stored as edges.

The mutable database application 162 may comprise computer-executableprogram code which may instruct the processing device 154 to performcertain logic, data processing, and data storing functions of theapplication to accomplish the entity's objectives. For instance, themutable database application 162 may receive input data and, based onthe input data, modify the configuration (e.g., data elements, datastructures, relationships, or the like) of the mutable database 164based on the input data. In particular, the mutable database application162 may detect the identity of users and/or computing systems accessingthe mutable database and/or the nature of the query or access request inorder to make configuration changes to the mutable database 164. In someembodiments, the mutable database application 162 may use artificialintelligence and/or neural networks to determine the optimalconfiguration of the mutable database 164 over a period of time via aniterative process. In such embodiments, the mutable database computingsystem may further comprise a neural network device which may include ahardware, software, or part hardware and software implementation of aneural network. Accordingly, the neural network may be a multilayerperceptron, Boltzmann machine, Markov chain, long/short term memory(LSTM), recurrent neural network (RNN), or the like.

As further illustrated in FIG. 1, the first entity computing system 104may be a computing system which is owned and/or operated by the entityfor executing various processes to achieve the entity's objectives. Inthis regard, the first entity computing system 104 may be, for example,a networked terminal, server, desktop computer, or the like, though itis within the scope of the disclosure for the first entity computingsystem 104 to be a portable device such as a cellular phone, smartphone, smart device, personal data assistant (PDA), laptop, or the like,which may be operated by a first user 101. The first entity computingsystem 104 generally comprises a communication device 112, a processingdevice 114, and a memory device 116, where the processing device 114 isoperatively coupled to the communication device 112 and the memorydevice 116. The processing device 114 uses the communication device 112to communicate with the network and other devices on the network, suchas, but not limited to the mutable database computing system 106 and/orthe second entity computing system 103. As such, the communicationdevice 112 generally comprises a modem, antennae, WiFi or Ethernetadapter, radio transceiver, or other device for communicating with otherdevices on the network.

The first entity computing system 104 comprises computer-readableinstructions 120 and data storage 118 stored in the memory device 116,which in one embodiment includes the computer-readable instructions 120of a first entity application 122. The first entity application 122 maycomprise executable code portions for performing functions related tothe various processes executed for the entity's purposes and objectives.In particular, the first user 101 may use the first entity computingsystem to access the mutable database 164 stored on the mutable databasecomputing system 164. The mutable database computing system 164 mayarrange the data elements within the mutable database 164 based oninformation such as the identity of the first user 101 and/or the firstentity computing system 104, the nature of the access request or query,metadata regarding the first user 101 (e.g., occupation, role within theentity, or the like). In some embodiments, the mutable database 164 maybe structured into an initial configuration based on inputs from thefirst user 101.

The operating environment 100 may further comprise a second entitycomputing system 103. The second entity computing system 103 may referto a second computing system which may be owned and/or operated by theentity to perform various functions related to the entity's objectives.In this regard, the second entity computing system 103 may be operatedby a second user 102 such as an employee of the entity. Accordingly, thesecond entity computing system 103 may also comprise a processing device174 operatively coupled to the communication device 172 and a memorydevice 176 comprising data storage 178 and computer readableinstructions 180.

The computer readable instructions 180 may comprise a second entityapplication 182 which may be configured to instruct the processingdevice 174 to execute certain functions over the network, such asinteracting with the mutable database computing system 106, applicationcomputing system 105, and/or the first entity computing system 104. Inparticular, the second entity application 182 may be used by the seconduser 102 to access the mutable database 164 within the mutable databasecomputing system 106. Based on the interactions of the mutable databasecomputing system 106 with the second entity computing system 103, theconfiguration of the mutable database 164 may be altered based on theidentity of the second user and/or the second entity computing system103, the nature of the query of the second user 102, metadata associatedwith the second user 102, or the like. In this way, the system mayprovide a first configuration of the mutable database 164 to the firstuser 101, while providing a second configuration of the mutable database164 to the second user 102.

The communication device 172, and other communication devices asdescribed herein, may comprise a wireless local area network (WLAN) suchas WiFi based on the Institute of Electrical and Electronics Engineers'(IEEE) 802.11 standards, Bluetooth short-wavelength UHF radio waves inthe ISM band from 2.4 to 2.485 GHz or other wireless access technology.Alternatively or in addition to the wireless interface, the secondentity computing system 103 may also include a communication interfacedevice that may be connected by a hardwire connection to the resourcedistribution device. The interface device may comprise a connector suchas a USB, SATA, PATA, SAS or other data connector for transmitting datato and from the respective computing system.

The computing systems described herein may each further include aprocessing device communicably coupled to devices as a memory device,output devices, input devices, a network interface, a power source, aclock or other timer, a camera, a positioning system device, agyroscopic device, one or more chips, and the like.

In some embodiments, the computing systems may access one or moredatabases or datastores (not shown) to search for and/or retrieveinformation related to the service provided by the entity. The computingsystems may also access a memory and/or datastore local to the variouscomputing systems within the operating environment 100.

The processing devices as described herein may include functionality tooperate one or more software programs or applications, which may bestored in the memory device. For example, a processing device may becapable of operating a connectivity program, such as a web browserapplication. In this way, the computing systems may transmit and receiveweb content, such as, for example, product valuation, serviceagreements, location-based content, and/or other web page content,according to a Wireless Application Protocol (WAP), Hypertext TransferProtocol (HTTP), and/or the like.

A processing device may also be capable of operating applications. Theapplications may be downloaded from a server and stored in the memorydevice of the computing systems. Alternatively, the applications may bepre-installed and stored in a memory in a chip.

The chip may include the necessary circuitry to provide integrationwithin the devices depicted herein. Generally, the chip will includedata storage which may include data associated with the service that thecomputing systems may be communicably associated therewith. The chipand/or data storage may be an integrated circuit, a microprocessor, asystem-on-a-chip, a microcontroller, or the like. In this way, the chipmay include data storage. Of note, it will be apparent to those skilledin the art that the chip functionality may be incorporated within otherelements in the devices. For instance, the functionality of the chip maybe incorporated within the memory device and/or the processing device.In a particular embodiment, the functionality of the chip isincorporated in an element within the devices. Still further, the chipfunctionality may be included in a removable storage device such as anSD card or the like.

A processing device may be configured to use the network interface tocommunicate with one or more other devices on a network. In this regard,the network interface may include an antenna operatively coupled to atransmitter and a receiver (together a “transceiver”). The processingdevice may be configured to provide signals to and receive signals fromthe transmitter and receiver, respectively. The signals may includesignaling information in accordance with the air interface standard ofthe applicable cellular system of the wireless telephone network thatmay be part of the network. In this regard, the computing systems may beconfigured to operate with one or more air interface standards,communication protocols, modulation types, and access types. By way ofillustration, the devices may be configured to operate in accordancewith any of a number of first, second, third, fourth, and/orfifth-generation communication protocols and/or the like. For example,the computing systems may be configured to operate in accordance withsecond-generation (2G) wireless communication protocols IS-136 (timedivision multiple access (TDMA)), GSM (global system for mobilecommunication), and/or IS-95 (code division multiple access (CDMA)), orwith third-generation (3G) wireless communication protocols, such asUniversal Mobile Telecommunications System (UMTS), CDMA2000, widebandCDMA (WCDMA) and/or time division-synchronous CDMA (TD-SCDMA), withfourth-generation (4G) wireless communication protocols, withfifth-generation (5G) wireless communication protocols, or the like. Thedevices may also be configured to operate in accordance withnon-cellular communication mechanisms, such as via a wireless local areanetwork (WLAN) or other communication/data networks.

The network interface may also include an application interface in orderto allow a user or service provider to execute some or all of theabove-described processes. The application interface may have access tothe hardware, e.g., the transceiver, and software previously describedwith respect to the network interface. Furthermore, the applicationinterface may have the ability to connect to and communicate with anexternal data storage on a separate system within the network.

The devices may have an interface that includes user output devicesand/or input devices. The output devices may include a display (e.g., aliquid crystal display (LCD) or the like) and a speaker or other audiodevice, which are operatively coupled to the processing device. Theinput devices, which may allow the devices to receive data from a seconduser 102, may include any of a number of devices allowing the devices toreceive data from a second user 102, such as a keypad, keyboard,touch-screen, touchpad, microphone, mouse, joystick, other pointerdevice, button, soft key, and/or other input device(s).

The devices may further include a power source. Generally, the powersource is a device that supplies electrical energy to an electricalload. In some embodiment, power source may convert a form of energy suchas solar energy, chemical energy, mechanical energy, or the like toelectrical energy. Generally, the power source may be a battery, such asa lithium battery, a nickel-metal hydride battery, or the like, that isused for powering various circuits, e.g., the transceiver circuit, andother devices that are used to operate the devices. Alternatively, thepower source may be a power adapter that can connect a power supply froma power outlet to the devices. In such embodiments, a power adapter maybe classified as a power source “in” the devices.

As described above, the computing devices as shown in FIG. 1 may alsoinclude a memory device operatively coupled to the processing device. Asused herein, “memory” may include any computer readable mediumconfigured to store data, code, or other information. The memory devicemay include volatile memory, such as volatile Random Access Memory (RAM)including a cache area for the temporary storage of data. The memorydevice may also include non-volatile memory, which can be embeddedand/or may be removable. The non-volatile memory may additionally oralternatively include an electrically erasable programmable read-onlymemory (EEPROM), flash memory or the like.

The memory device may store any of a number of applications or programswhich comprise computer-executable instructions/code executed by theprocessing device to implement the functions of the devices describedherein.

The computing systems may further comprise a gyroscopic device. Thepositioning system, input device, and the gyroscopic device may be usedin correlation to identify phases within a service term.

Each computing system may also have a control system for controlling thephysical operation of the device. The control system may comprise one ormore sensors for detecting operating conditions of the variousmechanical and electrical systems that comprise the computing systems orof the environment in which the computing systems are used. The sensorsmay communicate with the processing device to provide feedback to theoperating systems of the device. The control system may also comprisemetering devices for measuring performance characteristics of thecomputing systems. The control system may also comprise controllers suchas programmable logic controllers (PLC), proportional integralderivative controllers (PID) or other machine controllers. The computingsystems may also comprise various electrical, mechanical, hydraulic orother systems that perform various functions of the computing systems.These systems may comprise, for example, electrical circuits, motors,compressors, or any system that enables functioning of the computingsystems.

FIG. 2A illustrates a set of data elements within a first configurationof the mutable hierarchical database, in accordance with one embodimentof the present disclosure. The mutable database may contain data entriesrelated to data security. In this regard, the mutable database mayinclude, for instance, a first node 211 which is the parent to a secondnode 212 and a third node 313. The third node 313 may in turn be aparent to a fourth node 214 and a fifth node 215. The nodes mayrepresent particular computing capabilities which are arranged inrelationship to each other depending on the context in which thedatabase is accessed. Each node and/or relationship may be furtherdefined by properties or attributes which provide further details aboutthe node and/or relationship. For example, this first configuration ofthe mutable database may relate, in an exemplary embodiment, toprevention of data breaches or compromise. In such an embodiment, theability to detect malicious code may be the parent of a rootkitdetection capability. In some embodiments, the first configuration mayrepresent an initial configuration which is determined at theconstruction of the mutable database. In such embodiments, certain dataelements may be persistent across all configurations of the mutabledatabase (e.g., the first node 211 is always included in eachconfiguration). In other embodiments, the arrangement of data elementsmay be fluid such that the configuration of the database may notnecessarily include persistent data elements.

FIG. 2B illustrates the data elements within a second configuration ofthe mutable hierarchical database, in accordance with one embodiment ofthe present disclosure. The second configuration of the mutable databasemay be presented to a user when the mutable database is accessed from adifferent viewpoint or perspective than the viewpoint or perspectivefrom which the mutable database was accessed in the first configuration.The second configuration may be changed, for instance, when a seconduser or computing system accesses the database, the database is accessedfor a different purpose, or the like. For example, the secondconfiguration may be an arrangement of computing capabilities as theyrelate to data integrity, which may be related to the firstconfiguration, which is an arrangement of capabilities as they relate todata breaches or compromise. Accordingly, the second configuration mayinclude several of the capabilities (e.g., nodes) that existed withinthe first configuration, but with changed relationships (e.g., tworelated capabilities may have different relationships depending oncontext, such as data integrity vs. data breach). Said changes may bemade based on the properties or attributes of the nodes and/orrelationships. For example, the fourth node 214 within the secondconfiguration may be the parent of the third node 213, in contrast withthe first configuration. Moreover, certain nodes may be absent from thesecond configuration entirely if the node is not relevant to theperspective to which the second configuration is tailored. For example,if the fifth node 215 represents a capability that is relevant to thefirst configuration (e.g., relates to data breaches) but is not relevantto the second configuration (e.g., relates to data integrity), the fifthnode 215 may be absent from the second configuration, as depicted inFIG. 2B. In the manner described above, the process of creating multipleconfigurations may be repeated to provide viewpoint dependentreconfigurations of the database. In some embodiments, thereconfiguration process may be repeated each time the database isaccessed, thus resulting in a potentially infinite number ofconfigurations of the data elements within the mutable database.

FIG. 3 illustrates a process flow 300 for the mutable database system,in accordance with some embodiments of the present disclosure. Theprocess 300 begins at block 301, where the system generates a mutablehierarchical database, wherein the database comprises one or more dataelements. The data elements may comprise various types of datastructures within a database, such as data entries, nodes, edges,properties, or the like. In some embodiments, the database may be agraph database with one or more nodes being connected to other nodes viarelationships, where each node and/or relationship may be furtherdefined via properties or attributes. Accordingly, the database mayfurther be a hierarchical database with nodes existing within levelswithin the database (e.g., certain nodes may be higher or lower withinthe hierarchy in comparison to other nodes). To illustrate, arelationship between a first node and a second node may be defined as aparent-child relationship. In such an embodiment, the first node may beon a higher level within the hierarchical database in comparison to thesecond node.

The process continues to block 302, where the system receives a firstrequest to access the database. The first request may be received from afirst user and/or a first computing system, where the request maycomprise a query for data records within the mutable database. Saidquery may be further defined by a query type, or a stated objective orpurpose for accessing a database. For instance, the query may includerequests for data records related to or associated with a particularobjective, purpose, or perspective (e.g., data security). Accordingly,the first user may be an employee of the entity who has been tasked toobtain the data records with said purpose or perspective in mind. Insuch embodiments, the first request may further comprise informationabout the first user, such as title, role, membership in a particulardivision or team, or the like.

The process continues to block 303, where the system creates a firstconfiguration of the data elements within the database. The firstconfiguration of data elements may include a particular arrangement ofnodes, relationships, and/or properties based on the nature of the firstrequest. For example, based on the information within the first request(e.g., identity of the user, query type, data elements requested, or thelike), the system may arrange certain nodes into specific positionsand/or orientations within a hierarchy. Some nodes may be placed higheror lower in relation to other nodes, and nodes may be connected to oneanother via relationships within and across levels within the hierarchy.Continuing the above example, if the first request comprises a query fordata records relating to data security, the first configuration mayreflect an arrangement of data elements which is tailored to theperspective of data security. Once the first configuration has beengenerated, the system may present the first configuration (e.g., a copyof data elements and respective relationships) to the first user.

The process continues to block 304, where the system receives a secondrequest to access the database. The second request may include a queryfor data records from a different perspective in comparison to the firstrequest. Accordingly, the second request may be received from a seconduser and/or second computing system. That said, it is within the scopeof the disclosure for a second request to be submitted by the same user(e.g., the first user). For example, the second request may comprise aquery for data records relating to data integrity (in contrast to thefirst request, which may comprise a query for data records relating todata security).

The process concludes at block 305, where the system, based on thesecond request, creates a second configuration of the data elementswithin the database. The system may rearrange the data elements to beoptimally suitable for responding to the second request. For instance,the data elements may be modified based on the identity of the user whosubmitted the second request, the query type, purpose for which thedatabase is accessed, or the like. Continuing the above example, if thesecond request is submitted from the perspective of data integrity, thedatabase may be rearranged such that the data elements may be configuredto suit the perspective of data integrity. Accordingly, the system mayexecute one or more operations to rearrange the data elements, includingadding new nodes, excluding existing nodes, modifying relationships(e.g., changing the direction of the relationships, unlinking or linkingcertain nodes, or the like), adjusting the position of the nodes withinthe hierarchical structure, or the like. Once the system has generatedthe second configuration, the system may present the secondconfiguration of data elements to the user who submitted the secondrequest (e.g., the first user or the second user). The system may repeatthe process as described above to generate additional configurations(e.g., a third configuration, a fourth configuration, and the like) toaccount for additional perspectives from which the database is accessed.Accordingly, in some embodiments, the system may store the variousconfigurations of the database in a configuration repository such thatthe appropriate configuration may be recalled based on the query. Inother embodiments, the system may, rather than storing theconfigurations, generate each configuration at run time for each queryreceived (e.g., the database is reconstructed each time the database isqueried). In this way, the system may create a fluid database whichadapts to the various organizational needs of the entity.

Each communication interface described herein generally includeshardware, and, in some instances, software, that enables the computersystem, to transport, send, receive, and/or otherwise communicateinformation to and/or from the communication interface of one or moreother systems on the network. For example, the communication interfaceof the user input system may include a wireless transceiver, modem,server, electrical connection, and/or other electronic device thatoperatively connects the user input system to another system. Thewireless transceiver may include a radio circuit to enable wirelesstransmission and reception of information.

As will be appreciated by one of ordinary skill in the art, the presentinvention may be embodied as an apparatus (including, for example, asystem, a machine, a device, a computer program product, and/or thelike), as a method (including, for example, a business process, acomputer-implemented process, and/or the like), or as any combination ofthe foregoing. Accordingly, embodiments of the present invention maytake the form of an entirely software embodiment (including firmware,resident software, micro-code, and the like), an entirely hardwareembodiment, or an embodiment combining software and hardware aspectsthat may generally be referred to herein as a “system.” Furthermore,embodiments of the present invention may take the form of a computerprogram product that includes a computer-readable storage medium havingcomputer-executable program code portions stored therein.

As the phrase is used herein, a processor may be “configured to” performa certain function in a variety of ways, including, for example, byhaving one or more general-purpose circuits perform the function byexecuting particular computer-executable program code embodied incomputer-readable medium, and/or by having one or moreapplication-specific circuits perform the function.

It will be understood that any suitable computer-readable medium may beutilized. The computer-readable medium may include, but is not limitedto, a non-transitory computer-readable medium, such as a tangibleelectronic, magnetic, optical, infrared, electromagnetic, and/orsemiconductor system, apparatus, and/or device. For example, in someembodiments, the non-transitory computer-readable medium includes atangible medium such as a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EEPROM or Flash memory), a compact discread-only memory (CD-ROM), and/or some other tangible optical and/ormagnetic storage device. In other embodiments of the present invention,however, the computer-readable medium may be transitory, such as apropagation signal including computer-executable program code portionsembodied therein.

It will also be understood that one or more computer-executable programcode portions for carrying out the specialized operations of the presentinvention may be required on the specialized computer includeobject-oriented, scripted, and/or unscripted programming languages, suchas, for example, Java, Perl, Smalltalk, C++, SAS, SQL, Python, ObjectiveC, and/or the like. In some embodiments, the one or morecomputer-executable program code portions for carrying out operations ofembodiments of the present invention are written in conventionalprocedural programming languages, such as the “C” programming languagesand/or similar programming languages. The computer program code mayalternatively or additionally be written in one or more multi-paradigmprogramming languages, such as, for example, F #.

Embodiments of the present invention are described above with referenceto flowcharts and/or block diagrams. It will be understood that steps ofthe processes described herein may be performed in orders different thanthose illustrated in the flowcharts. In other words, the processesrepresented by the blocks of a flowchart may, in some embodiments, be inperformed in an order other that the order illustrated, may be combinedor divided, or may be performed simultaneously. It will also beunderstood that the blocks of the block diagrams illustrated, in someembodiments, merely conceptual delineations between systems and one ormore of the systems illustrated by a block in the block diagrams may becombined or share hardware and/or software with another one or more ofthe systems illustrated by a block in the block diagrams. Likewise, adevice, system, apparatus, and/or the like may be made up of one or moredevices, systems, apparatuses, and/or the like. For example, where aprocessor is illustrated or described herein, the processor may be madeup of a plurality of microprocessors or other processing devices whichmay or may not be coupled to one another. Likewise, where a memory isillustrated or described herein, the memory may be made up of aplurality of memory devices which may or may not be coupled to oneanother.

It will also be understood that the one or more computer-executableprogram code portions may be stored in a transitory or non-transitorycomputer-readable medium (e.g., a memory, and the like) that can directa computer and/or other programmable data processing apparatus tofunction in a particular manner, such that the computer-executableprogram code portions stored in the computer-readable medium produce anarticle of manufacture, including instruction mechanisms which implementthe steps and/or functions specified in the flowchart(s) and/or blockdiagram block(s).

The one or more computer-executable program code portions may also beloaded onto a computer and/or other programmable data processingapparatus to cause a series of operational steps to be performed on thecomputer and/or other programmable apparatus. In some embodiments, thisproduces a computer-implemented process such that the one or morecomputer-executable program code portions which execute on the computerand/or other programmable apparatus provide operational steps toimplement the steps specified in the flowchart(s) and/or the functionsspecified in the block diagram block(s). Alternatively,computer-implemented steps may be combined with operator and/orhuman-implemented steps in order to carry out an embodiment of thepresent invention.

While certain exemplary embodiments have been described and shown in theaccompanying drawings, it is to be understood that such embodiments aremerely illustrative of, and not restrictive on, the broad invention, andthat this invention not be limited to the specific constructions andarrangements shown and described, since various other changes,combinations, omissions, modifications and substitutions, in addition tothose set forth in the above paragraphs, are possible. Those skilled inthe art will appreciate that various adaptations and modifications ofthe just described embodiments can be configured without departing fromthe scope and spirit of the invention. Therefore, it is to be understoodthat, within the scope of the appended claims, the invention may bepracticed other than as specifically described herein.

What is claimed is:
 1. A system for restructuring electronic dataelements within a mutable hierarchical database, the system comprising:a memory device with computer-readable program code stored thereon; acommunication device; and a processing device operatively coupled to thememory device and the communication device, wherein the processingdevice is configured to execute the computer-readable program code to:generate the mutable hierarchical database, wherein the mutablehierarchical database comprises one or more data elements; receive afirst request to access the mutable hierarchical database; based on thefirst request, create a first configuration of the data elements withinthe mutable hierarchical database; receive a second request to accessthe mutable hierarchical database; and based on the second request,create a second configuration of the data elements within the mutablehierarchical database.
 2. The system according to claim 1, wherein theone or more data elements comprise nodes, edges, and properties, whereincreating the first configuration of the data elements and creating thesecond configuration of the data elements comprises at least one ofadding nodes, removing nodes, modifying relationships, modifyingproperties, or changing hierarchical positions of nodes.
 3. The systemaccording to claim 1, wherein the first request is associated with afirst objective and submitted by a first user, wherein the firstconfiguration of the data elements is associated with the firstobjective, wherein the second request is associated with a secondobjective and submitted by a second user, wherein the secondconfiguration of the data elements is associated with the secondobjective.
 4. The system according to claim 3, wherein thecomputer-readable program code further causes the processing device to:present the first configuration of the data elements to the first user;and present the second configuration of the data elements to the seconduser.
 5. The system according to claim 1, wherein the first request isassociated with a first objective and submitted by a first user, whereinthe first configuration of the data elements is associated with thefirst objective, wherein the second request is associated with a secondobjective and submitted by the first user, wherein the secondconfiguration of the data elements is associated with the secondobjective.
 6. The system according to claim 5, wherein thecomputer-readable program code further causes the processing device topresent the first configuration of the data elements and the secondconfiguration of the data elements to the first user.
 7. The systemaccording to claim 1, wherein the computer-readable program code furthercauses the processing device to store the first configuration of thedata elements and the second configuration of the data elements within aconfiguration repository.
 8. A computer program product forrestructuring electronic data elements within a mutable hierarchicaldatabase, the computer program product comprising at least onenon-transitory computer readable medium having computer-readable programcode portions embodied therein, the computer-readable program codeportions comprising executable code portions for: generating the mutablehierarchical database, wherein the mutable hierarchical databasecomprises one or more data elements; receiving a first request to accessthe mutable hierarchical database; based on the first request, creatinga first configuration of the data elements within the mutablehierarchical database; receiving a second request to access the mutablehierarchical database; and based on the second request, creating asecond configuration of the data elements within the mutablehierarchical database.
 9. The computer program product according toclaim 8, wherein the one or more data elements comprise nodes, edges,and properties, wherein creating the first configuration of the dataelements and creating the second configuration of the data elementscomprises at least one of adding nodes, removing nodes, modifyingrelationships, modifying properties, or changing hierarchical positionsof nodes.
 10. The computer program product according to claim 8, whereinthe first request is associated with a first objective and submitted bya first user, wherein the first configuration of the data elements isassociated with the first objective, wherein the second request isassociated with a second objective and submitted by a second user,wherein the second configuration of the data elements is associated withthe second objective.
 11. The computer program product according toclaim 10, wherein the computer-readable program code portions furthercomprise executable code portions for: presenting the firstconfiguration of the data elements to the first user; and presenting thesecond configuration of the data elements to the second user.
 12. Thecomputer program product according to claim 8, wherein the first requestis associated with a first objective and submitted by a first user,wherein the first configuration of the data elements is associated withthe first objective, wherein the second request is associated with asecond objective and submitted by the first user, wherein the secondconfiguration of the data elements is associated with the secondobjective.
 13. The computer program product according to claim 12,wherein the computer-readable program code portions further compriseexecutable code portions for presenting the first configuration of thedata elements and the second configuration of the data elements to thefirst user.
 14. A computer-implemented method for restructuringelectronic data elements within a mutable hierarchical database, whereinthe method comprises: generating the mutable hierarchical database,wherein the mutable hierarchical database comprises one or more dataelements; receiving a first request to access the mutable hierarchicaldatabase; based on the first request, creating a first configuration ofthe data elements within the mutable hierarchical database; receiving asecond request to access the mutable hierarchical database; and based onthe second request, creating a second configuration of the data elementswithin the mutable hierarchical database.
 15. The computer-implementedmethod according to claim 14, wherein the one or more data elementscomprise nodes, edges, and properties, wherein creating the firstconfiguration of the data elements and creating the second configurationof the data elements comprises at least one of adding nodes, removingnodes, modifying relationships, modifying properties, or changinghierarchical positions of nodes.
 16. The computer-implemented methodaccording to claim 14, wherein the first request is associated with afirst objective and submitted by a first user, wherein the firstconfiguration of the data elements is associated with the firstobjective, wherein the second request is associated with a secondobjective and submitted by a second user, wherein the secondconfiguration of the data elements is associated with the secondobjective.
 17. The computer-implemented method according to claim 16,the method further comprising: presenting the first configuration of thedata elements to the first user; and presenting the second configurationof the data elements to the second user.
 18. The computer-implementedmethod according to claim 14, wherein the first request is associatedwith a first objective and submitted by a first user, wherein the firstconfiguration of the data elements is associated with the firstobjective, wherein the second request is associated with a secondobjective and submitted by the first user, wherein the secondconfiguration of the data elements is associated with the secondobjective.
 19. The computer-implemented method according to claim 18,the method further comprising presenting the first configuration of thedata elements and the second configuration of the data elements to thefirst user.
 20. The computer-implemented method according to claim 14,the method further comprising storing the first configuration of thedata elements and the second configuration of the data elements within aconfiguration repository.